Implement wrapper method of issue_stateless_channel_token#981
Merged
Implement wrapper method of issue_stateless_channel_token#981
Conversation
habara-k
force-pushed
the
wrapper-of-issue-stateless-channel-token
branch
2 times, most recently
from
ecc9228 to
5284e3a
Compare
habara-k
force-pushed
the
wrapper-of-issue-stateless-channel-token
branch
from
5284e3a to
b54c301
Compare
Yang-33
approved these changes
Apr 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
issue_stateless_channel_token_by_jwt_assertion()andissue_stateless_channel_token_by_client_secret()oneOf), but the generatedissue_stateless_channel_token()merges them into a single method where all parameters are required. Previously, users had to pass empty strings for unused parameters. These wrappers auto-fill them.Test plan
tests/api/test_issue_stateless_channel_token.py— verifies correct form parameters are sent for each authentication patternResolves #823